Self-configuring ssd multi-protocol support in host-less environment

ABSTRACT

A device that may configure itself is disclosed. The device may include an interface that may be used for communications with a chassis. The interface may support a plurality of transport protocols. The device may include a Vital Product Data (VPD) reading logic to read a VPD from the chassis and a built-in self-configuration logic to configure the interface to use one of the transport protocols and to disable alternative transport protocols, responsive to the VPD.

RELATED APPLICATION DATA

This application is a continuation of U.S. patent application Ser. No. 16/844,995, filed Apr. 9, 2020, now allowed, which is a continuation of U.S. patent application Ser. No. 15/256,495, filed Sep. 2, 2016, now allowed, which claims the benefit of U.S. Provisional Patent Application Ser. No. 62/366,622, filed Jul. 26, 2016, all of which are incorporated by reference herein for all purposes.

FIELD

The inventive concepts relate generally to Solid State Drives (SSDs), and more particularly to SSDs that may support multiple transport protocols and that may configure themselves in host machines.

BACKGROUND

Modern storage devices use many different interfaces, such as Serial AT Attachment (SATA), Serial Attached Small Computer System Interface (SCSI) (SAS), and Non-Volatile Memory Express (NVMe), among others, to connect to host machines. Host systems and operating systems are required to support these multi-protocol/device environments. For example, faster or higher performing devices may be assigned and used as cache or a higher tier by the OS/driver/VM/application. Slower devices may be used as a lower tier of storage etc.

From a hardware perspective, storage devices are designed and programmed to be a fixed specific device by the manufacturers. For example, manufacturers must decide upfront that the devices should be classified as SAS or SATA respectively before shipping out. Once manufactured and shipped, a customer might not make any protocol changes afterward.

Host operating systems and applications must be designed to handle a variety of mixed devices. This required robustness in terms of hardware support results in operating system and application complexity and expense. Conventionally, all storage devices are required to inform the host whether to use SATA, SAS, enterprise NVMe, or other transport protocols. The host operating systems is then required to perform bus enumeration and discover all of these devices. In a large system, this process takes several minutes to complete.

A need remains for a way for devices to configure themselves based on information about the chassis into which the devices are installed.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a chassis with a self-configuring device installed therein, according to an embodiment of the inventive concept.

FIG. 2 shows additional details of the chassis of FIG. 1 .

FIG. 3 shows details of the storage device of FIG. 1 .

FIG. 4 shows various information being written to the Vital Product Data (VPD) of FIG. 1 .

FIG. 5 shows the built-in self-configuration logic using the VPD reading logic and VPD writing logic of FIG. 3 to interact with the Vital Product Data of FIG. 1 .

FIG. 6 shows the storage device of FIG. 3 after self-configuration.

FIGS. 7A-7F show a flowchart of an example procedure for the device of FIG. 1 to self-configure to a number of different transport protocols, according to an embodiment of the inventive concept.

FIG. 8 shows a flowchart of an example procedure for the device of FIG. 1 to self-configure.

FIG. 9 shows a flowchart of an example procedure for the VPD writing logic of FIG. 3 to write information to the Vital Product Data of FIG. 1 .

DETAILED DESCRIPTION

Reference will now be made in detail to embodiments of the inventive concept, examples of which are illustrated in the accompanying drawings. In the following detailed description, numerous specific details are set forth to enable a thorough understanding of the inventive concept. It should be understood, however, that persons having ordinary skill in the art may practice the inventive concept without these specific details. In other instances, well-known methods, procedures, components, circuits, and networks have not been described in detail so as not to unnecessarily obscure aspects of the embodiments.

It will be understood that, although the terms first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first module could be termed a second module, and, similarly, a second module could be termed a first module, without departing from the scope of the inventive concept.

The terminology used in the description of the inventive concept herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the inventive concept. As used in the description of the inventive concept and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. The components and features of the drawings are not necessarily drawn to scale.

Newer storage devices (or other devices, such as Network Interface Cards (NICs)) may use transport protocols such as Non-Volatile Memory Express (NVMe) over Fabrics (NVMeoF) to communicate with a chassis (also termed a host machine), and may support multiple transport protocols. When such devices are installed in a chassis, these devices may perform self-discovery during boot up and initialization. These devices may read Vital Product Data from a known location in an Electrically Erasable Programmable Read Only Memory (EEPROM). These devices may then discover that they are installed in an NVMeoF chassis. These devices may then configure themselves to enable, for example, the Ethernet ports and disabling other unnecessary/unused/unsupported transport protocol support. In this way the operating system and host CPU overhead related to multiple transport protocol discovery and management may be avoided. In a large storage system, using such self-configuring devices will shorten the enumeration process significantly because all devices may perform self-discovery independently by reading from a known location from the system. Host CPUs and operating systems are not required to be present.

FIG. 1 shows a chassis with a self-configuring device installed therein, according to an embodiment of the inventive concept. In FIG. 1 , chassis 105 is shown. Chassis 105 may also be referred to as a host machine, or host for short. Chassis 105 may include various components, such as processor 110, memory 115, Electronically Erasable Programmable Read Only Memory (EEPROM) 120, and device 125. Processor 110 may be any variety of processor: for example, an Intel Xeon, Celeron, Itanium, or Atom processor, an AMD Opteron processor, an ARM processor, etc. Memory 115 may be any variety of memory, such as flash memory, Static Random Access Memory (SRAM), Persistent Random Access Memory, Ferroelectric Random Access Memory (FRAM), or Non-Volatile Random Access Memory (NVRAM), such as Magnetoresistive Random Access Memory (MRAM) etc., but is typically DRAM.

EEPROM 120 may store Vital Product Data (VPD) 130. Vital Product Data 130 may be data used by device 125 to configure itself. For example, Vital Product Data 130 may store information about chassis 105 or about the transport protocol intended to be used to communicate with device 125. Example transport protocols that may be used to communicate with device 125 may include Ethernet, Fibre Channel, InfiniBand, or Non-Volatile Memory Express (NVMe), to name a few. Vital Product Data 130 may also store information about transport sub-protocols used. For example, if Vital Product Data 130 specifies that the Ethernet transport protocol is to be used, Vital Product Data 130 may store whether to use Remote Direct Memory Access (RDMA) over Converged Ethernet (RoCE) or iWarp, among other possibilities.

While FIG. 1 shows Vital Product Data 130 as being stored within EEPROM 120, embodiments of the inventive concept may support using any alternative storage mediums. For example, EEPROM 120 may be replaced with an Erasable Programmable Read Only Memory (EPROM) or flash memory, to name a few alternatives.

Device 125 may be any variety of device that may be self-configured. Examples of such devices may include storage devices and Network Interface Cards (NICs). Within the category of storage devices, Solid State Drives (SSDs) are one possibility for storage device, but other storage forms, such as hard disk drives or other long-term storage devices, are also viable.

Another type of device that may benefit from self-configuration is an intelligent device, such as an Ethernet or other variety of Solid State Drive (SSD) with an embedded processor running an embedded operating system. When chassis 105 boots up, the intelligent device may start before the embedded operating system begins. The intelligent device may then perform self-configuration. When the embedded operating system begins running, the intelligent device may perform software configuration as well, as needed.

In the remainder of this document, references to storage devices are intended to encompass other types of devices that may benefit from self-configuration, with changes to the internal components of the device as appropriate to the function of the device.

FIG. 2 shows additional details of chassis 105 of FIG. 1 . Referring to FIG. 2 , typically, chassis 105 include one or more processors 110, which may include memory controller 205 and clock 210, which may be used to coordinate the operations of the components of chassis 105. Processors 110 may also be coupled to memory 115, which may include random access memory (RAM), read-only memory (ROM), or other state preserving media, as examples. Processors 110 may also be coupled to storage devices 125, and to network connector 215, which may be, for example, an Ethernet connector or a wireless connector. Processors 110 may also be connected to a bus 220, to which may be attached user interface 225 and input/output interface ports that may be managed using input/output engine 230, among other components.

FIG. 3 shows details of storage device 125 of FIG. 1 . In FIG. 3 , storage device 125 may include interface 305, VPD reading logic 310, built-in self-configuration logic 315, VPD writing logic 320, and data storage 325. Interface 305 may represent both a physical connection to chassis 105 of FIG. 1 and the transport protocol(s) used in communications between storage device 125 and chassis 105 of FIG. 1 , or communications with devices outside of the chassis 105 (i.e., other computers over a network). VPD reading logic 310 may read Vital Product Data 130 of FIG. 1 from EEPROM 120 of FIG. 1 via any bus, such as System Management Bus (SMBus) or Inter-Integrated Circuit (I2C or I²C) bus. Built-in self-configuration logic 315 may configure interface 305 by enabling the transport protocol(s) supported by chassis 105 of FIG. 1 and disabling any transport protocols supported by storage device 125 but not supported by chassis 105 of FIG. 1 . VPD writing logic 320 may write information to Vital Product Data 130 of FIG. 1 via a bus, similar to VPD reading logic 310. Data storage 325, of course, may store user data.

FIG. 3 also shows some example transport protocols that may be represented by interface 305. For example, transport protocols NVMe 330, RoCE 335, iWarp 340, Fibre Channel 345, and InfiniBand 350 may be transport protocols supported by storage device 125.

While the above describes RoCE 335 and iWarp 340 as transport protocols, RoCE 335 and iWarp 335 may be considered variations of Ethernet transport protocol 355. In some embodiments of the inventive concept, Ethernet 355 may be considered a transport protocol, with RoCE 335 and iWarp 340 as transport sub-protocols. In addition, while FIG. 3 does not show transport sub-protocols for other transport protocols, such as NVMe 330, Fibre Channel 345, or InfiniBand 350, embodiments of the inventive concept may support sub-channels for these other transport protocols as well.

FIG. 4 shows various information being written to Vital Product Data 130 of FIG. 1 . In FIG. 4 , Vital Product Data 130 may include a data structure designed to store information pertinent to chassis 105 of FIG. 1 . This information stored in Vital Product Data 130 may include:

-   -   Storage class 405, identifying a type of storage device 125 of         FIG. 3 supported by the chassis such as NVMe, NVMeoF, Internet         Small Computer System Interface (iSCSI), Fibre Channel, SAS,         SATA, etc.     -   Transport protocol 410, identifying the transport protocol(s)         supported by chassis 105 of FIG. 1 .     -   Transport sub-protocol 415, identifying a transport sub-protocol         supported by chassis 105 of FIG. 1 .     -   Chassis firmware 420, identifying the firmware revision in use         by chassis 105 of FIG. 1 .     -   Multi-path Input/Output (I/O) 425, which, if enabled, identifies         chassis 105 of FIG. 1 as a high availability system. Any single         ported storage device installed in such a chassis should disable         itself in favor of multi-port storage device.     -   Minimum firmware revision 430, specifying a minimum firmware         revision for device 125 of FIG. 1 . If the firmware revision of         device 125 of FIG. 1 is below the specified threshold, then         device 125 of FIG. 1 should report that it needs a firmware         update by writing to a report status region of Vital Product         Data 130.

Vital Product Data 130 may also include storage for information written by storage device 125 of FIG. 3 . This information that may be written to Vital Product Data 130 may include:

-   -   Incompatibility 435, explaining why storage device 125 of FIG. 3         might not operate within chassis 105 of FIG. 1 . One reason why         storage device 125 of FIG. 3 might be incompatible with chassis         105 of FIG. 1 would be protocol incompatibility 440, such as         when storage device 125 of FIG. 3 might not support Ethernet         transport protocol but is installed in a chassis that uses         Ethernet transport protocol for communication. Another example         of protocol incompatibility 440 would be when chassis 105 of         FIG. 1 needs a particular transport sub-protocol that storage         device 125 of FIG. 3 does not support: for example, a RoCE         device installed in an iWarp chassis. Another reason why storage         device 125 of FIG. 3 might be incompatible with chassis 105 of         FIG. 1 would be when storage device 125 of FIG. 3 is incorrect         type 445, such as when chassis 105 of FIG. 1 needs a High         Availability device, but storage device 125 of FIG. 3 is not a         High Availability device, or chassis 105 of FIG. 1 needs a dual         port device and storage device 125 of FIG. 1 is only a single         port device.     -   Device ID 450, identifying the device installed in chassis 105         of FIG. 1 .     -   Device firmware 455, identifying the current firmware revision         of storage device 125 of FIG. 3 .

FIG. 5 shows built-in self-configuration logic 315 using VPD reading logic 310 and VPD writing logic 320 of FIG. 3 to interact with Vital Product Data 130 of FIG. 1 . In FIG. 5 , VPD reading logic 310 may read data from Vital Product Data 130, as shown by arrow 505. Additionally, VPD writing logic 320 may write information to Vital Product Data 130, as shown by arrow 510. Examples of information that may be written by VPD writing logic 320 to Vital Product Data 130 may include device ID 450 of FIG. 4 , device firmware revision 455 of FIG. 4 , and incompatibility information 435 of FIG. 4 .

FIG. 6 shows storage device 125 of FIG. 3 after self-configuration. In FIG. 6 , storage device 125 has accessed Vital Product Data 130 of FIG. 1 , which has indicated that chassis 105 of FIG. 1 uses the Ethernet transport protocol, with the RoCE transport sub-protocol. As a result, storage device 125 has disabled NVMe transport protocol 330, Fibre Channel transport protocol 345, InfiniBand transport protocol 350, and Ethernet iWarp transport protocol 340 (or sub-protocol, depending on the embodiment of the inventive concept), as shown by the large X symbols. Only Ethernet RoCE transport protocol 335 (or sub-protocol) is enabled.

FIGS. 7A-7F show a flowchart of an example procedure for device 125 of FIG. 1 to self-configure to a number of different transport protocols, according to an embodiment of the inventive concept. In FIG. 7A, at block 703, device 125 of FIG. 1 may boot up. At block 706, built-in self-configuration logic 315 of FIG. 3 may use VPD reading logic 310 of FIG. 3 to access Vital Product Data 130 of FIG. 1 from EEPROM 120 of FIG. 1 .

Starting with block 709, device 125 of FIG. 1 may determine whether it may be self-configured to chassis 105 of FIG. 1 , and how to do so. At block 709, device 125 of FIG. 1 may determine from Vital Product Data 130 of FIG. 1 whether chassis 105 of FIG. 1 requires a High Availability device. If so, then at block 712, device 125 of FIG. 1 may determine whether it is a two-port device, as might be required for a High Availability device. If device 125 of FIG. 1 is not a two-port device, then at block 715 built-in self-configuration logic 315 of FIG. 3 may report an error condition: perhaps by using VPD writing logic 320 of FIG. 3 to write incompatibility information 445 of FIG. 4 to Vital Product Data 130 of FIG. 1 .

Otherwise, chassis 105 of FIG. 1 does not require a High Availability device, or device 125 of FIG. 1 is a High Availability device. Either way, at block 718 (FIG. 7B), device 125 of FIG. 1 may determine whether chassis 105 of FIG. 1 expects to use NVMe transport protocol 330 of FIG. 3 . If chassis 105 of FIG. 1 expects to use NVMe transport protocol 330 of FIG. 3 , then at block 721 device 125 of FIG. 1 may determine if it supports NVMe transport protocol 330 of FIG. 3 . If device 125 of FIG. 1 supports NVMe transport protocol 330 of FIG. 3 , then at block 724 device 125 of FIG. 1 may self-configure to enable NVMe transport protocol 330 and to disable other transport protocols. Otherwise, control returns to block 715 for built-in self-configuration logic 315 of FIG. 3 to report an error condition, perhaps by using VPD writing logic 320 of FIG. 3 to write incompatibility information 440 to Vital Product Data 130 of FIG. 1 .

If at block 718 chassis 105 of FIG. 1 did not expect to use NVMe transport protocol 330 of FIG. 3 for communications, then at block 727 (FIG. 7C), device 125 of FIG. 1 may determine whether chassis 105 of FIG. 1 expects to use Fibre Channel transport protocol 345 of FIG. 3 . If chassis 105 of FIG. 1 expects to use Fibre Channel transport protocol 345 of FIG. 3 , then at block 730 device 125 of FIG. 1 may determine if it supports Fibre Channel transport protocol 345 of FIG. 3 . If device 125 of FIG. 1 supports Fibre Channel transport protocol 345 of FIG. 3 , then at block 733 device 125 of FIG. 1 may self-configure to enable Fibre Channel transport protocol 345 and to disable other transport protocols. Otherwise, control returns to block 715 for built-in self-configuration logic 315 of FIG. 3 to report an error condition, perhaps by using VPD writing logic 320 of FIG. 3 to write incompatibility information 440 to Vital Product Data 130 of FIG. 1 .

If at block 727 chassis 105 of FIG. 1 did not expect to use Fibre Channel transport protocol 345 of FIG. 3 for communications, then at block 736 (FIG. 7D), device 125 of FIG. 1 may determine whether chassis 105 of FIG. 1 expects to use InfiniBand transport protocol 350 of FIG. 3 . If chassis 105 of FIG. 1 expects to use InfiniBand transport protocol 350 of FIG. 3 , then at block 739 device 125 of FIG. 1 may determine if it supports InfiniBand transport protocol 350 of FIG. 3 . If device 125 of FIG. 1 supports InfiniBand transport protocol 350 of FIG. 3 , then at block 742 device 125 of FIG. 1 may self-configure to enable InfiniBand transport protocol 350 and to disable other transport protocols. Otherwise, control returns to block 715 for built-in self-configuration logic 315 of FIG. 3 to report an error condition, perhaps by using VPD writing logic 320 of FIG. 3 to write incompatibility information 440 to Vital Product Data 130 of FIG. 1 .

If at block 736 chassis 105 of FIG. 1 did not expect to use InfiniBand transport protocol 350 of FIG. 3 for communications, then at block 745 (FIG. 7E), device 125 of FIG. 1 may determine whether chassis 105 of FIG. 1 expects to use Ethernet transport protocol 355 of FIG. 3 . If chassis 105 of FIG. 1 expects to use Ethernet transport protocol 355 of FIG. 3 , then at block 748 device 125 of FIG. 1 may determine if it supports Ethernet transport protocol 355 of FIG. 3 . If device 125 of FIG. 1 does not support Ethernet transport protocol 355 of FIG. 3 , then control returns to block 715 for built-in self-configuration logic 315 of FIG. 3 to report an error condition, perhaps by using VPD writing logic 320 of FIG. 3 to write incompatibility information 440 to Vital Product Data 130 of FIG. 1 .

If at block 748 device 125 of FIG. 1 does support Ethernet transport protocol 355 of FIG. 3 , then at block 751 (FIG. 7F), built-in self-configuration logic 315 of FIG. 3 may use VPD reading logic 310 of FIG. 3 to determine if Vital Product Data 130 of FIG. 1 specifies RoCE transport protocol 335 of FIG. 3 as a selected transport sub-protocol. If so, then at block 754, device 125 of FIG. 10 may self-configure to enable RoCE transport sub-protocol 335 and to disable other transport protocols/sub-protocols. Otherwise, at block 757, built-in self-configuration logic 315 of FIG. 3 may use VPD reading logic 310 of FIG. 3 to determine if Vital Product Data 130 of FIG. 1 specifies iWarp transport protocol 340 of FIG. 3 as a selected transport sub-protocol. If so, then at block 760, device 125 of FIG. 10 may self-configure to enable iWarp transport sub-protocol 340 and to disable other transport protocols/sub-protocols. Otherwise, at block 763, device 125 may self-configure to enable generic Ethernet transport protocol 355 of FIG. 3 and to disable other transport protocols. Processing may then end.

While FIGS. 7A-7F show built-in self-configuration logic 315 considered both transport protocols and sub-protocols, other embodiments of the inventive concept may consider only protocols. For example, instead of FIGS. 7E-7F, other embodiments of the inventive concept may include sheets similar to FIGS. 7B-7D, specifically considering RoCE protocol 335 of FIG. 3 and iWarp protocol 340 of FIG. 3 .

In addition, FIGS. 7A-7F, some embodiments of the inventive concept are shown. For example, FIGS. 7A-7F show device 125 of FIG. 1 considering four transport protocols—NVMe transport protocol 330, Ethernet transport protocol 355, Fibre Channel transport protocol 345, and InfiniBand transport protocol 350, all of FIG. 3 —and two transport sub-protocols—Ethernet RoCE transport sub-protocol 335 and Ethernet iWarp transport sub-protocol 340, both of FIG. 3 . But embodiments of the inventive concept may be extended to support any number of transport protocols, each of which may include any number of transport sub-protocols (including zero). In addition, device 125 of FIG. 1 may consider the transport protocols in any desired order, not only that shown in FIGS. 7A-7F. All such variations are considered to be within the scope of the inventive concept.

FIG. 8 shows a flowchart of an example procedure for device 125 of FIG. 1 to self-configure, according to an embodiment of the inventive concept. FIG. 8 is a more generalized version of FIGS. 7A-7F. In FIG. 8 , at block 805, built-in self-configuration logic 315 of FIG. 3 may, using VPD reading logic 310 of FIG. 3 , request access to Vital Product Data 130 of FIG. 1 , stored in EEPROM 120 of FIG. 1 . At block 810, device 125 of FIG. 1 may receive Vital Product Data 130 of FIG. 1 . At block 815, device 125 of FIG. 1 may identify a transport protocol to use from Vital Product Data 130 of FIG. 1 . At block 820, device 125 of FIG. 1 may identify a transport sub-protocol to use from Vital Product Data 130 of FIG. 1 . At block 825, device 125 may self-configure to use the identified transport protocol/sub-protocol, by enabling and disabling transport protocols/sub-protocols as appropriate. Finally, at block 830, built-in self-configuration logic 315 of FIG. 3 may, using VPD writing logic 320 of FIG. 3 , write information to Vital Product Data 130 of FIG. 1 . As described above, such information may include, for example, an incompatibility of type or transport protocol between chassis 105 of FIG. 1 and device 125 of FIG. 1 .

As discussed above with reference to FIG. 3 , instead of considering RoCE 335 and iWarp 340, both of FIG. 3 , as sub-protocols of Ethernet protocol 355 of FIG. 3 , RoCE 335 and iWarp 340, both of FIG. 3 , may be considered to be their own protocols. To support such embodiments of the inventive concept, block 820 may be omitted.

FIG. 9 shows a flowchart of an example procedure for VPD writing logic 320 of FIG. 3 to write information to Vital Product Data 130 of FIG. 1 , according to an embodiment of the inventive concept. In FIG. 9 , at block 905, VPD writing logic 320 of FIG. 3 may write device identifier 450 of FIG. 4 to Vital Product Data 130 of FIG. 1 . Alternatively or additionally, at block 910, VPD writing logic 320 of FIG. 3 may write device firmware revision 455 of FIG. 4 to Vital Product Data 130 of FIG. 1 . Alternatively or additionally, at block 915, VPD writing logic 320 of FIG. 3 may write incompatibility information 435 of FIG. 4 to Vital Product Data 130 of FIG. 1 , indicating why device 125 of FIG. 1 will not operate in chassis 105 of FIG. 1 .

In FIGS. 7A-9 , some embodiments of the inventive concept are shown. But a person skilled in the art will recognize that other embodiments of the inventive concept are also possible, by changing the order of the blocks, by omitting blocks, or by including links not shown in the drawings. All such variations of the flowcharts are considered to be embodiments of the inventive concept, whether expressly described or not.

The following discussion is intended to provide a brief, general description of a suitable machine or machines in which certain aspects of the inventive concept may be implemented. The machine or machines may be controlled, at least in part, by input from conventional input devices, such as keyboards, mice, etc., as well as by directives received from another machine, interaction with a virtual reality (VR) environment, biometric feedback, or other input signal. As used herein, the term “machine” is intended to broadly encompass a single machine, a virtual machine, or a system of communicatively coupled machines, virtual machines, or devices operating together. Exemplary machines include computing devices such as personal computers, workstations, servers, portable computers, handheld devices, telephones, tablets, etc., as well as transportation devices, such as private or public transportation, e.g., automobiles, trains, cabs, etc.

The machine or machines may include embedded controllers, such as programmable or non-programmable logic devices or arrays, Application Specific Integrated Circuits (ASICs), embedded computers, smart cards, and the like. The machine or machines may utilize one or more connections to one or more remote machines, such as through a network interface, modem, or other communicative coupling. Machines may be interconnected by way of a physical and/or logical network, such as an intranet, the Internet, local area networks, wide area networks, etc. One skilled in the art will appreciate that network communication may utilize various wired and/or wireless short range or long range carriers and protocols, including radio frequency (RF), satellite, microwave, Institute of Electrical and Electronics Engineers (IEEE) 802.11, Bluetooth®, optical, infrared, cable, laser, etc.

Embodiments of the present inventive concept may be described by reference to or in conjunction with associated data including functions, procedures, data structures, application programs, etc. which when accessed by a machine results in the machine performing tasks or defining abstract data types or low-level hardware contexts. Associated data may be stored in, for example, the volatile and/or non-volatile memory, e.g., RAM, ROM, etc., or in other storage devices and their associated storage media, including hard-drives, floppy-disks, optical storage, tapes, flash memory, memory sticks, digital video disks, biological storage, etc. Associated data may be delivered over transmission environments, including the physical and/or logical network, in the form of packets, serial data, parallel data, propagated signals, etc., and may be used in a compressed or encrypted format. Associated data may be used in a distributed environment, and stored locally and/or remotely for machine access.

Embodiments of the inventive concept may include a tangible, non-transitory machine-readable medium comprising instructions executable by one or more processors, the instructions comprising instructions to perform the elements of the inventive concepts as described herein.

Having described and illustrated the principles of the inventive concept with reference to illustrated embodiments, it will be recognized that the illustrated embodiments may be modified in arrangement and detail without departing from such principles, and may be combined in any desired manner. And, although the foregoing discussion has focused on particular embodiments, other configurations are contemplated. In particular, even though expressions such as “according to an embodiment of the inventive concept” or the like are used herein, these phrases are meant to generally reference embodiment possibilities, and are not intended to limit the inventive concept to particular embodiment configurations. As used herein, these terms may reference the same or different embodiments that are combinable into other embodiments.

The foregoing illustrative embodiments are not to be construed as limiting the inventive concept thereof. Although a few embodiments have been described, those skilled in the art will readily appreciate that many modifications are possible to those embodiments without materially departing from the novel teachings and advantages of the present disclosure. Accordingly, all such modifications are intended to be included within the scope of this inventive concept as defined in the claims.

Embodiments of the inventive concept may extend to the following statements, without limitation:

Statement 1. An embodiment of the inventive concept includes a device, comprising:

-   -   an interface to a chassis, the interface capable of supporting a         plurality of transport protocols for communicating between the         storage device and the chassis;     -   a VPD reading logic to read a Vital Product Data from the         chassis; and     -   a built-in self-configuration logic to configure the interface         to use one of the plurality of transport protocols and to         disable alternative transport protocols of the plurality of         transport protocols responsive to the Vital Product Data.

Statement 2. An embodiment of the inventive concept includes a device according to statement 1, wherein the device includes a Network Interface Card (NIC).

Statement 3. An embodiment of the inventive concept includes a device according to statement 1, wherein:

-   -   the device includes a storage device; and     -   the storage device further includes storage for data.

Statement 4. An embodiment of the inventive concept includes a device according to statement 3, wherein the plurality of transport protocols include Ethernet, Fibre Channel, and InfiniBand.

Statement 5. An embodiment of the inventive concept includes a device according to statement 4, wherein the plurality of transport protocols further includes a transport sub-protocol drawn from a set including Remote Direct Memory Access (RDMA) over Converged Ethernet (RoCE) and iWarp.

Statement 6. An embodiment of the inventive concept includes a device according to statement 3, wherein the interface includes a Non-Volatile Memory Express over Fabric (NVMeoF) interface.

Statement 7. An embodiment of the inventive concept includes a device according to statement 3, further comprising VPD writing logic to write information to the Vital Product Data.

Statement 8. An embodiment of the inventive concept includes a device according to statement 7, wherein the information written to the Vital Product Data includes at least one of a protocol incompatibility between the storage device and chassis, and an incorrect type of storage device.

Statement 9. An embodiment of the inventive concept includes a non-transitory memory for storing a Vital Product Data, comprising:

-   -   a data structure stored in said non-transitory memory, said data         structure including:     -   a first storage for a transport protocol to be used by a device,         the transport protocol drawn from a set including Ethernet,         Fibre Channel, InfiniBand, and Non-Volatile Memory Express         (NVMe);     -   a second storage for a first data written by the device, the         first data specifying an identifier for the device; and     -   a third storage for data written by the device, the data         specifying a reason why the device might not operate within a         chassis.

Statement 10. An embodiment of the inventive concept includes a non-transitory memory according to statement 9, wherein the data structure further includes a fourth storage for a transport sub-protocol to be used by the device, the transport sub-protocol drawn from a set including Remote Direct Memory Access (RDMA) over Converged Ethernet (RoCE) and iWarp.

Statement 11. An embodiment of the inventive concept includes a non-transitory memory according to statement 9, wherein the data structure further includes a fifth storage to store a firmware revision of the chassis.

Statement 12. An embodiment of the inventive concept includes a non-transitory memory according to statement 9, wherein the data structure further includes a sixth storage to store a firmware revision of the device.

Statement 13. An embodiment of the inventive concept includes a method, comprising:

-   -   requesting by a device a Vital Product Data from a chassis;     -   receiving at the device the Vital Product Data from the chassis;     -   identifying a transport protocol to use responsive to the Vital         Product Data; and     -   configuring the device to use the identified transport protocol         and disabling alternative transport protocols in the device.

Statement 14. An embodiment of the inventive concept includes a method according to statement 13, wherein:

-   -   requesting by a device a Vital Product Data from a chassis         includes requesting by a storage device the Vital Product Data         from the chassis;     -   receiving at the device the Vital Product Data from the chassis         includes receiving at the storage device the Vital Product Data         from the chassis; and     -   configuring the device to use the identified transport protocol         and disabling alternative transport protocols in the storage         device includes configuring the storage device to use the         identified transport protocol and disabling alternative         transport protocols in the storage device.

Statement 15. An embodiment of the inventive concept includes a method according to statement 14, wherein the transport protocol to use drawn from a set including Ethernet, Fibre Channel, and InfiniBand.

Statement 16. An embodiment of the inventive concept includes a method according to statement 15, wherein identifying a transport protocol to use responsive to the Vital Product Data further includes identifying a transport sub-protocol to use responsive to the Vital Product Data drawn from a set further including Remote Direct Memory Access (RDMA) over Converged Ethernet (RoCE) and iWarp.

Statement 17. An embodiment of the inventive concept includes a method according to statement 14, further comprising writing information by the storage device to the Vital Product Data.

Statement 18. An embodiment of the inventive concept includes a method according to statement 17, wherein the information may include at least one of a device identifier, a reason why the storage device does not operate in the chassis, and a firmware revision of the storage device.

Statement 19. An embodiment of the inventive concept includes a method according to statement 18, wherein the reason why the storage device does not operate in the chassis may include at least one of a protocol incompatibility between the storage device and chassis, and an incorrect type of storage device.

Statement 20. An embodiment of the inventive concept includes a method according to statement 14, wherein:

-   -   requesting by a storage device a Vital Product Data from a         chassis includes requesting by the storage device the Vital         Product Data from a chassis over a Non-Volatile Memory Express         over Fabric (NVMeoF) interface; and     -   receiving at the storage device the Vital Product Data from the         chassis includes receiving at the storage device the Vital         Product Data from the chassis over the NVMeoF interface.

Statement 21. An embodiment of the inventive concept includes an article, comprising a tangible storage medium, the tangible storage medium having stored thereon non-transitory instructions that, when executed by a machine, result in:

-   -   requesting by a device a Vital Product Data from a chassis;     -   receiving at the device the Vital Product Data from the chassis;     -   identifying a transport protocol to use responsive to the Vital         Product Data; and     -   configuring the device to use the identified transport protocol         and disabling alternative transport protocols in the device.

Statement 22. An embodiment of the inventive concept includes an article according to statement 21, wherein:

-   -   requesting by a device a Vital Product Data from a chassis         includes requesting by a storage device the Vital Product Data         from the chassis;     -   receiving at the device the Vital Product Data from the chassis         includes receiving at the storage device the Vital Product Data         from the chassis; and     -   configuring the device to use the identified transport protocol         and disabling alternative transport protocols in the storage         device includes configuring the storage device to use the         identified transport protocol and disabling alternative         transport protocols in the storage device.

Statement 23. An embodiment of the inventive concept includes an article according to statement 22, wherein the transport protocol to use drawn from a set including Ethernet, Fibre Channel, and InfiniBand.

Statement 24. An embodiment of the inventive concept includes an article according to statement 23, wherein identifying a transport protocol to use responsive to the Vital Product Data further includes identifying a transport sub-protocol to use responsive to the Vital Product Data drawn from a set further including Remote Direct Memory Access (RDMA) over Converged Ethernet (RoCE) and iWarp.

Statement 25. An embodiment of the inventive concept includes an article according to statement 22, the tangible storage medium having stored thereon further non-transitory instructions that, when executed by the machine, result in:

-   -   writing information by the storage device to the Vital Product         Data.

Statement 26. An embodiment of the inventive concept includes an article according to statement 25, wherein the information may include at least one of a device identifier, a reason why the storage device does not operate in the chassis, and a firmware revision of the storage device.

Statement 27. An embodiment of the inventive concept includes an article according to statement 26, wherein the reason why the storage device does not operate in the chassis may include at least one of a protocol incompatibility between the storage device and chassis, and an incorrect type of storage device.

Statement 28. An embodiment of the inventive concept includes an article according to statement 22, wherein:

-   -   requesting by a storage device a Vital Product Data from a         chassis includes requesting by the storage device the Vital         Product Data from a chassis over a Non-Volatile Memory Express         over Fabric (NVMeoF) interface; and     -   receiving at the storage device the Vital Product Data from the         chassis includes receiving at the storage device the Vital         Product Data from the chassis over the NVMeoF interface.

Consequently, in view of the wide variety of permutations to the embodiments described herein, this detailed description and accompanying material is intended to be illustrative only, and should not be taken as limiting the scope of the inventive concept. What is claimed as the inventive concept, therefore, is all such modifications as may come within the scope and spirit of the following claims and equivalents thereto. 

1. A device, comprising: an interface to a chassis, the interface supporting at least a first transport protocol and a second transport protocol for communicating between the device and the chassis; a circuit to identify a configuration of the chassis, the configuration including the first transport protocol intended to be used by the chassis to communicate with the device; and a self-configuration logic to configure the interface to lock the interface to the first transport protocol responsive to the configuration.
 2. A device according to claim 1, wherein the first transport protocol and the second transport protocol are drawn from a set including Ethernet, Fibre Channel, and InfiniBand, Non-Volatile Memory Express (NVMe), and NVMe over Fabrics (NVMe-oF).
 3. A device according to claim 2, wherein the first transport protocol and the second transport protocol are drawn from the set further including Remote Direct Memory Access (RDMA) over Converged Ethernet (RoCE) and iWarp.
 4. A device according to claim 1, further comprising writing logic to write information to the device.
 5. A device according to claim 4, wherein the information written to the device includes at least one of a protocol incompatibility between the device and chassis, and an incorrect type of device.
 6. A non-transitory memory for storing a data, comprising: a data structure stored in said non-transitory memory, said data structure including: a first storage for a transport protocol to be used by a device, the transport protocol drawn from a set including Ethernet, Fibre Channel, InfiniBand, Non-Volatile Memory Express (NVMe), and NVMe over Fabrics (NVMe-oF); and a second storage for a first data written by the device, the first data specifying an identifier for the device.
 7. A non-transitory memory according to claim 6, wherein the data structure further includes a third storage for data written by the device, the data specifying a reason why the device might not operate within a chassis.
 8. A non-transitory memory according to claim 6, wherein the data structure further includes a third storage for a transport sub-protocol to be used by the device, the transport sub-protocol drawn from a set including Remote Direct Memory Access (RDMA) over Converged Ethernet (RoCE) and iWarp.
 9. A non-transitory memory according to claim 6, wherein the data structure further includes a third storage to store a firmware revision of the chassis.
 10. A non-transitory memory according to claim 6, wherein the data structure further includes a third storage to store a firmware revision of the device.
 11. A method, comprising: requesting a configuration of a chassis over a interface by a device, the device capable of using a first transport protocol or a second transport protocol to communicate with the chassis; receiving at the device the configuration of the chassis over the interface; identifying the first transport protocol to use responsive to the configuration; and configuring the device to lock the interface to the first transport protocol.
 12. A method according to claim 11, wherein the first transport protocol and the second transport protocol are drawn from a set including Ethernet, Fibre Channel, InfiniBand, Non-Volatile Memory Express (NVMe), and NVMe over Fabrics (NVMe-oF).
 13. A method according to claim 12, wherein identifying a first transport protocol to use responsive to the data further includes identifying a transport sub-protocol to use responsive to the data, the transport sub-protocol drawn from a set further including Remote Direct Memory Access (RDMA) over Converged Ethernet (RoCE) and iWarp.
 14. A method according to claim 11, further comprising writing information by the device.
 15. A method according to claim 14, wherein the information includes at least one of a device identifier, a reason why the device does not operate in the chassis, and a firmware revision of the device.
 16. A method according to claim 15, wherein the reason why the device does not operate in the chassis includes at least one of a protocol incompatibility between the device and chassis and an incorrect type of device. 